System and method for identifying data streams associated with medical equipment

ABSTRACT

A system and method for uniquely identifying data streams associated with medical equipment are described. The system may be implemented in a variety of ways, including as a combination of a medical device, a data stream identifier, and a medical device identifier. The medical device generates a plurality of data streams. The data streams are uninterrupted transmissions of data from the medical device. The data streams include information regarding the operation of the medical device. The data stream identifier attaches a unique data tag to the data streams. The medical device identifier is configured to generate a medical device tag. The medical device tag includes information to uniquely identify the medical device and is accessible from an external computer. The data stream identifier and the medical device identifier are secured to the medical device.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is a continuation-in-part of copending U.S.utility applications entitled: “Medical Treatment Verification Systemand Method,” having Ser. No. 10/135,180 and filed Apr. 30, 2002 which isincorporated herein by reference; and “System and Method for OperatingMedical Devices,” having Ser. No. 10/059,929 and filed Jan. 29, 2002which is incorporated herein by reference. Application Ser. No.10/135,180 is a continuation-in-part of copending U.S. utilityapplication Ser. No. 10/059,929.

TECHNICAL FIELD

[0002] This invention relates generally to a system and method foroperating medical devices and communication with such devices. Theinvention relates to a system and method for verifying that the rightmedication is provided to the right patient in the right dose at theright time, and via the right route. More particularly, the inventionrelates to a system and method for uniquely identifying data streamsassociated with medical equipment.

BACKGROUND OF THE INVENTION

[0003] Patient care systems typically include computer networks, medicaldevices for treating a patient, and controls for the medical devices.Although patient care systems have been improved through the use ofcomputerized automation systems and methods, patient care systemscontinue to rely heavily upon manual data management processes formedical devices and controls for medical devices. For example, nursingstations are typically connected to the computer networks in modernhospitals, but it is unusual for the computer network to extend to apatient's room. Computer networks offer the opportunity for automateddata management processing including the operating and monitoring ofmedical devices and controls for the medical devices at thepoint-of-care. Despite advances in the field, automated data managementtechnology has been underutilized for point-of-care applications due toa lack of more efficient systems and methods for operating medicaldevices such as infusion pumps.

[0004] One of the great hazards in the medical field is the possibilityof errors in medication delivery systems due to human error. Computernetworks have the potential to minimize the hazards of errors inmedication delivery due to human error. Computer networks have thepotential for relating medical equipment and patients in order tominimize the possibility of medication errors. Medication errors may becaused by misidentification of medical devices and the lack of ormisidentification of data streams associated with computerized medicaldevices. In order to minimize the possibility of medication errors, theindustry is in need of more efficient systems and methods for uniquelyidentifying data streams associated with medical equipment.

SUMMARY OF THE INVENTION

[0005] The present invention provides a system and method for uniquelyidentifying data streams associated with medical equipment. The systemcan be implemented in a variety of ways, including as a combination of amedical device, a data stream identifier, and a medical deviceidentifier. The medical device generates a plurality of data streams.The data streams are uninterrupted transmissions of data from themedical device. The data streams include information regarding theoperation of the medical device. The data stream identifier attaches aunique data tag to the data streams. The medical device identifier isconfigured to generate a medical device tag. The medical device tagincludes information to uniquely identify the medical device and isaccessible from an external computer. The data stream identifier and themedical device identifier are secured to the medical device.

[0006] When implemented as a method, the invention can be implemented ina variety of ways, including as a combination of the following steps:generating a plurality of data streams with a medical device, generatinga unique data tag using a data stream identifier; attaching the uniquedata tag to the data streams; and generating a medical device tag uponrequest from an external computer. The data streams are uninterruptedtransmissions of data from the medical device and include informationregarding the operation of the medical device. A medical deviceidentifier is accessible from an external computer and generates themedical device tag to uniquely identify the medical device. The datastream identifier and the medical device identifier are secured to themedical device.

[0007] Other systems, methods, features, and advantages of the presentinvention will be, or will become, apparent to one having ordinary skillin the art upon examination of the following drawings and detaileddescription. It is intended that all such additional systems, methods,features, and advantages included within this description, be within thescope of the present invention, and be protected by the accompanyingclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The invention can be better understood with reference to thefollowing drawings. The components in the drawings are not necessarilyto scale, emphasis instead being placed upon clearly illustrating theprinciples of the present invention. In the drawings, like referencenumerals designate corresponding parts throughout the several views.

[0009]FIG. 1 is a graphical representation of a patient care system. Thepatient care system includes a pharmacy computer and a central computersystem. The patient care system also includes a digital assistant and amedical device at a treatment location;

[0010]FIG. 2 is a block diagram of the medical device of FIG. 1;

[0011]FIG. 3 is a block diagram showing functional components of thepatient care system of FIG. 1;

[0012]FIG. 4 is a block diagram of a computer system representative ofthe pharmacy computer, the central system, and/or the digital assistantof FIG. 1. The computer system can include portions of the system foruniquely identifying data streams associated with medical equipment. Thecomputer system can be used in the method and system of uniquelyidentifying data streams associated with medical equipment; and,

[0013]FIG. 5 is a flowchart showing an exemplar embodiment of the methodfor uniquely identifying data streams associated with medical equipmentthat can be practiced as a computer program in the computer system ofFIG. 4.

DETAILED DESCRIPTION

[0014]FIG. 1 is a graphical representation of an embodiment of a patientcare system 100. In the embodiment, the patient care system 100 includesa pharmacy computer 104, a central computer system 108, and a treatmentlocation 106. Medical equipment at the treatment location 106 includes adigital assistant 118, a medical treatment cart 132, and an infusionpump 120. The patient care system 100, the central computer system 108,and the treatment location 106 are linked by a network 102. In anembodiment, the pharmacy computer 104 can include a processing unit 104a, a keyboard 104 b, a video display 104 c, a printer 104 d, a bar codereader 104 e, and a mouse 104 f. Although not shown in FIG. 1, thepatient care system 100 can also include subsystems for hospitaladministration, nursing stations, a clinical information subsystem, ahospital information subsystem, an Admissions Discharge and Transfer(ADT) subsystem, a billing subsystem, and/or other subsystems typicallyincluded in patient care systems.

[0015] In an embodiment, the central system 108 includes a centralservicing unit 108 a, a database 108 b, a video display 108 c, a barcode reader 108 e, other input/output components, and many othercomponents known to those having ordinary skill in the art. The network102 can include a cable communication system 110 portion and a wirelesscommunication system portion. The cable communication system 110 can be,but is not limited to, an Ethernet cabling system, and a thin netsystem.

[0016] In an embodiment, the treatment location 106 includes the medicalequipment and a treatment bed 106 a. In FIG. 1, a clinician 116 and apatient 112 are shown in the treatment location 106. Medication 124 canbe of a type administered to the patient 112 by using the infusion pump120. Medication 124 can also be of a type administered without using aninfusion pump. Infusion pump 120 can be, but is not limited to, the typethat administers medication from an infusion bag or the type thatadministers medication through a syringe. Medication 124 can be storedin medication storage areas 132 a of medical treatment cart 132. Theclinician 116 uses a hand-held computer, such as digital assistant 118,while administering medication 124 to the patient 112.

[0017] In the course of treating patient 112, the clinician 116 can usethe digital assistant 118 to communicate with the other portions of thesystem 100 via cable communication system 110 and a first wirelesscommunication path 126. The infusion pump 120 can have the ability tocommunicate with the system 100 via cable communication system 110 andsecond wireless communication path 128 through methods such as, but notlimited to Bluetooth and Wifi technologies. Medical treatment cart 132can also have the ability to communicate via a wireless communicationpath (not shown in FIG. 1). A wireless transceiver 114 interfacesbetween the wireless communication devices and cable communicationsystem 110. The wireless communication system portion of the network canemploy technology such as, but not limited to, those known to personshaving ordinary skill in the art such as IEEE 802.11a, IEEE 802.11b“Wireless Ethernet” through 802.11g, Bluetooth, a local area network,wireless local area networks, a network having a tree topography, anetwork having a ring topography, wireless internet point of presencesystems, an Ethernet, the Internet, radio communications, infrared,fiber optic, and telephone. Though shown in FIG. 1 as a wirelesscommunication system, any of the communication paths shown can also behardwired communication paths, if desired.

[0018] In an embodiment, infusion pump 120 can also have the ability tocommunicate with the cable communication system 110 via cablecommunication path 140. Bridge 142 provides an interface between cablecommunication path 140 and cable communication system 110. Though, shownin FIG. 1 as communicating with a single infusion pump 120, the systemdescribed herein for identifying data streams associated with medicalequipment allows for the bridge 142 to communicate with a plurality ofinfusion pumps through a plurality of ports 214 (FIG. 2).

[0019] In the patient care system 100, a physician (not shown) can ordermedication 124 for patient 112. Alternatively, the order can alsooriginate with a clinician 116 at the treatment location 106. Thephysician and/or clinician 116 can use a computerized physician orderentry system (CPOE) and/or the medical treatment cart 132 to order themedication 124 for the patient 112. Those having ordinary skill in theart are familiar with basic CPOE systems. Despite its name, anyclinician 116 can use the CPOE. If the medication 124 is one that isefficient to administer through infusion pump 120, the order includesinformation for generating operating parameters for the infusion pump120. The operating parameters are the information and/or instruction setthat is necessary to program a medical device, such as an infusion pump120, to operate in accordance with the order.

[0020] The order can be entered in the pharmacy computer 104 viainput/output devices such as the keyboard 104 b, the mouse 104 f, atouch screen display, the CPOE system and/or the medical treatment cart132. Those having ordinary skill in the art are familiar with these andsimilar input/output devices. The processing unit 104 a is able totransform a manually entered order into computer readable data. Devicessuch as the computerized prescribing order entry system can transform anorder into computer readable data prior to introduction to theprocessing unit 104 a. The operating parameters can then be printed in abar code format by the printer 104 d on a medication label 124 a. Themedication label 124 a can then be affixed to a medication 124container. The medication 124 container is then transported to thetreatment location 106. The medication 124 can then be administered tothe patient 112 in a variety of ways known in the art including orallyand through an infusion pump 120. If the medication 124 is administeredorally, the clinician 116 can communicate via the digital assistant 118and/or the medical treatment cart 132. Medical treatment cart 132 iscomputerized and generally has a keyboard (not shown), a display 132 b,and other input/output devices such as a bar code scanner (not shown).It is also possible, if desired, to enter the order at the treatmentlocation 106 using the digital assistant 118, medical treatment cart132, and/or input devices associated with the infusion pump 120.

[0021] As indicated previously, at the treatment location the medication124 can be mounted on the infusion pump 120 wherein an intravenous (IV)line 130 is run from the infusion pump 120 to the patient 112. Theinfusion pump 120 can include a pumping unit 120 a, a keypad 120 b, adisplay 120 c, an infusion pump ID 120 d, an antenna 120 e (forBluetooth, Wifi, or other tadio technology transmission and/orreception) and a bar code reader 120 f. The barcode reader 120 f can beincorporated into the infusion pump 120 housing or may be connected viaa communication cable. Infusion pumps not originally equipped withwireless capability can be provided with a wireless adaptor (not shown)for assisting in the identification of data streams. The wirelessadaptor can use a short-range radio technology such as Bluetooth, along-range radio technology such as Wifi, or other radio technology.Moreover, the wireless adaptor can have its own battery if necessary toavoid reducing the battery life of the host infusion pump, or thewireless adaptor can operate from power supplied by the infusion pump.In an embodiment, the wireless adaptor can also use intelligent datamanagement such as, but not limited to, store and forward datamanagement and data compression to minimize power consumption. Thewireless adaptor can also include the ability to communicate with thedigital assistant 118 even when the network 102 is not functioning.

[0022] The patient care system 100 can include a variety of identifierssuch as, but not limited to, personnel, equipment, and medicationidentifiers. As shown in FIG. 1, the clinician 116 has a clinician badge116 a identifier, the patient 112 has a wristband 112 a identifier, themedical device has an equipment identifier (For example, the infusionpump 120 can have an infusion pump ID 120 d identifier), and themedication 124 has a medication label 124 a identifier. Clinician badge116 a, wristband 112 a, infusion pump ID 120 d, and medication label 124a include information to identify the personnel, equipment, andmedication they are associated with. If desired, the identifiers canalso have additional information. For example, the medication label 124a can include information regarding the intended recipient of themedication 124, operating parameters for infusion pump 120, andinformation regarding the lot number and expiration of medication 124.The information included in the identifiers can be printed, but ispreferably in a device readable format such as, but not limited to, anoptical readable device format such as a bar code, a radio frequency(RF) device readable format such as an RFID, an iButton, a smart card,and a laser readable format. The digital assistant 118 can include adisplay 118 a and can have the ability to read the identifiers includingbiometric information such as a fingerprint.

[0023] The wristband 112 a is preferably attached to the patient 112 asthe patient 112 enters a medical care facility. As stated previously,the wristband 112 a includes a patient identifier. The patientidentifier can include printed information to identify the patient andadditional information such as a treating physician's name(s). Thepatient identifier for patient 112 can include information such as, butnot limited to, the patient's name, age, social security number, thepatient's blood type, address, allergies, a hospital ID number, and thename of a patient's relative.

[0024]FIG. 2 is a block diagram 200 of the medical device of FIG. 1.Consistent with FIG. 1, the medical device is depicted as an infusionpump 120. The components of infusion pump 120 are analogous to manyother medical device components known to those having ordinary skill inthe art. While infusion pump 120 is used to describe the system andmethod for uniquely identifying data streams associated with medicaldevice and equipment, the invention can be employed with any medicaldevices or equipment that communicates via network 102 (FIG. 1). FIG. 2includes a data stream identifier 204 and a medical device identifier206 secured to infusion pump 120. Although not necessary, the datastream identifier 204 and the medical device identifier 206 can bepackaged in the same housing 208 and they can be electricallyinterconnected in order to efficiently complete their respective tasks.The housing 208 can be incorporated into a connector 210, such as butnot limited to, a DB 9 connector, or similar connectors known to thosehaving ordinary skill in the art. In other embodiments, the data streamidentifier 204 and the medical device identifier 206 can be packedinside of the infusion pump housing 212.

[0025] Infusion pump 120 can include an equipment ID, such as infusionpump ID 120 d, and a bar code reader 120 f and a communication port 120g. Infusion pump ID 120 d can be a bar code label. The communicationport 120 g can be a conventional communication port, such as but notlimited to, a serial communication port, a RS232, a RS485, and othercommunication ports known to those having ordinary skill in the art.

[0026] Infusion pump 120 provides data to network 102 (FIG. 1). The datais in the form of data packets. The data packets are also known as datastreams. As used herein, “data packets” and “data streams” both refer toa preferably uninterrupted, but not necessarily, package of data asrecognized by the network. In other words, the terms refer to a packageof data that the network 102 recognizes as coming from a singleoriginating point and in a grouping that the network 102 processes as adiscrete grouping of data from the medical device. The system foridentifying data identifies the data streams originating from a medicaldevice such that the network can identify all data from the medicaldevice as originating from the medical device. Therefore, the exact sizeand characteristics of the data stream are dependent upon thecharacteristics of the medical device and the network. Regardless of theexact size and characteristics of the data stream, the data streamcontains information regarding the operation of the medical device, suchas but not limited to, a flow rate, an occlusion setting, alarms andoperating parameters.

[0027] Data streams pass through communication port 120 g to bridge 142via the cable communication path 140. Alternatively, as indicatedpreviously and described in detail further herein, the data streams passfrom antenna 120 e to wireless transceiver 114, via wirelesscommunication path 128.

[0028] In an embodiment, bridge 142 can have a plurality of ports 214.In bridge 142, the data stream interacts with the identifying dataproduced by the data stream identifier 204 and medical device identifier206. Bridge 142 interfaces with cable communication system 110. Theidentified data streams then exits the bridge 142. The identified datastreams can then interact with other data traffic in network 102.

[0029] The data stream identifier 204 can be incorporated into a DallasSemiconductor DS 2505-UNW or the like. When a DS 2505-UNW is employed asthe data stream identifier 204, the data stream identifier 204 canconnect to pin 9 of a connector 210 such as the DB9 connector. Theidentifying data can be stored in memory elements, such as but notlimited to, ROM elements, EEPROM memory elements, OTP EPROM memoryelements, and NV SRAM memory elements. If the data stream identifier isconnected to pin 9, the other 8 pins of the DB9 connector are free topass the data stream from the serial port 120 g to the cablecommunication path 140.

[0030] The medical device identifier 206 includes a programmable memoryelement that may be programmed to store data to identify the medicaldevice. The stored data can include, but is not limited to, theinformation stored on the infusion pump ID 120 d, the type of medicaldevice, the baud rate, the service dates, and asset tags. Asset tags areinventory tags that uniquely identify the device they are associatedwith such as a serial number or other assigned identifier. Preferably,the memory element can be a one-time programmable memory element suchas, but not limited to, an EEPROM memory element and an OTP EPROM memoryelement. The data stored on the memory element can be the data that thedata stream identifier 204 attaches to the data streams in order toidentify the data streams. In other embodiments, the data stored on thememory element can be provided upon an inquiry from the network 102.When a DS 2505-UNW and a DB9 connector are employed, the data stored onthe memory element can be passed to the cable communication path 140 viapin 9 of the DB9.

[0031] The data stream identifier 204 and the medical device identifier206 can be packaged in the same housing 208. For example, the DS2505-UNWfrom Dallas Semiconductor includes a data stream identifier 204 and aprogrammable EEPROM in the same housing. In one embodiment, the housing208 is physically secured to the medical device so that if the medicaldevice is disconnected from the cable communication path 140 or bridge142 and moved to another part of the network 102, the network 102 willstill recognize the data streams generated by the medical device asoriginating at the medical device.

[0032] Bridge 142 can include a plurality of serial ports 214 tocommunicate with a plurality of medical devices. The bridge 142 serialports 214 include a pin for communication of the identifying dataassociated with the data streams. Bridge 142 merges the unidentifieddata stream from the medical device with the identifying data from thedata stream identifier 204. The output of bridge 142 is the identifieddata stream. The unidentified data stream can enter bridge 142 through aplurality of serial port pins. For example, the unidentified data streamcan enter bridge 142 on pins 1-8 of serial port 214 and the identifyingdata can enter bridge 142 on pin 9 of serial port 214. Bridge 142 can bea smart client bridge. Bridge 142 includes software to read theidentifying data of the data stream. Bridge 142 can also be configuredto only communicate with medical equipment that is associated with datastream identifiers 204.

[0033] In a wireless data stream identification system, bridge 142 mayinterface with a wireless network access point such as transceiver 114.If bridge 142 is configured to interface with a wireless network accesspoint, then bridge 142 can be mounted on the medical device and operablyconnected to antenna 120 e so that the medical device is portablethroughout the patient care system 100. Bridge 142 can be a device, suchas but not limited to, a Serial Client Bridge by Symbol Technologies,Inc., a CT WLAN Serial Client Bridge by CyberTEC GmbH, a Bluetoothdevice, a Wifi device, a combination or Bluetooth and Wifi, aSpectrum24® Serial Client Bridge, or the like.

[0034] The programming of the medical device identifier 206 with theattributes of any particular medical device can be accomplished usingextendable markup language (XML) and UniqueWare. Using programming suchas UniqueWare, the data stream identifier 204 and the medical deviceidentifier 206 can be associated with the medical device by connectingthe cabled communication path 140 to the connector 210. One pin of theconnector 210 can then be used to communicate with the data streamidentifier 204 and the medical device identifier 206. The information tobe communicated to program the medical device identifier can be readusing a bar code reader, such as bar code readers 108 e and 104 e andscanners 338 (FIG. 3), to read the bar code label of the medicalequipment. Programming software, such as UniqueWare, will then downloadthe medical device ID to the medical device identifier 206. Thisinformation can then be accessible to the data stream identifier 204.The Unique Ware can also create a table to associate a plurality ofmedical devices with a plurality of medical device identifiers.

[0035]FIG. 3 is a block diagram showing functional components of thepatient care system 100 of FIG. 1. Some functional blocks of FIG. 3include the ability to communicate using the current invention. Forexample, various functional blocks communicate with medical device 332in FIG. 3. The system and method for uniquely identifying data streamsassociated with medical equipment can be practiced as a modular systemwhere the modules represent various functions of the patient care system100. FIG. 3 presents the system for uniquely identifying data streamsassociated with medical equipment as a system for identifying datastreams. The flexibility of the system can be enhanced when the systemis practiced as a modular system. The modules of the system can beincluded in various portions of the patient care system 100. The patientcare system 100 includes a medication management module 302, aprescription generation module 304, a prescription activation module306, and a prescription authorization module 308.

[0036] The medication management module 302 can coordinate the functionsof the other modules in the patient care system 100 that are involved inthe administration of medical treatment. The medication managementmodule 302 will generally coordinate with other portions of the patientcare system 100. The medication module 302 can include sub-modules foroperating and/or interfacing with a CPOE, for operating and/orcommunicating with point-of-care modules, and for operating and/orcommunicating with medical treatment comparison modules. In FIG. 3, anadmissions, discharge, and transfer (ADT) interface 310, a billinginterface 312, a lab interface 314, and a pharmacy interface 316 areshown. ADT interface 310 can be used to capture information such as thepatient's size, weight, and allergies. Pharmacy interface 3164 importsorders from the pharmacy. The pharmacy interface 316 can be an HL7 typeof interface that interfaces with other systems for entering orders,such as a CPOE. This ability reduces the necessity for entering datainto the patient care system 100 more than once. The pharmacy interface316 can be configured to communicate with commercially available systemssuch as, but not limited to Cerner, HBOC, Meditech, SMS, and Phamous.Various other interfaces are also known to those having ordinary skillin the art but are not shown in FIG. 3 for clarity.

[0037] The medication management module 302 can have additional featuressuch as the ability to check for adverse reactions due to drug-to-drugincompatibility, duplicate drug administration, drug allergies, drugdosage limitations, drug frequency limitations, drug durationlimitations, and drug disease contraindications. Food and alcoholinteractions can also be noted. Drug limitations can include limitationssuch as, but not limited to, limitations associated with adults,children, infants, newborns, premature births, geriatric adults, agegroupings, weight groupings, height groupings, and body surface area.Generally, the medication management module 302 can prevent the entry ofthe same prescription for the same patient from two different sourceswithin the patient care system 100.

[0038] The medication management module 302 can also include the abilityto generate reports. The reports include, but are not limited to,end-of-shift, titration information, patient event lists, infusionhistory, pump performance history, pump location history, and pumpmaintenance history. The end-of-shift report can include the pumpchannel, start time, end time, primary infusion, piggyback infusion,medication, dose, rate, pump status, volume infused, volume remaining,time remaining, and the last time cleared. The infusion history reportincludes medications and volume infused.

[0039] The medication management module 302 can also include a medicalequipment status database. The medical equipment status databaseincludes data indicating the location of a medical device 332 within thepatient care system 100. The medical equipment status database can alsoinclude data indicating the past performance of a medical device 332.The medical equipment status database can also include data indicatingthe maintenance schedule and/or history of a medical device 332.

[0040] The prescription generation module 304 generates hardprescriptions and electronic (E-copy) prescriptions. Hard prescriptionsare generally produced in triplicate in medical facilities. A first hardcopy 318 is generally sent to the pharmacy, a second hard copy 320 isgenerally kept for the patient's records, and third hard copy 322 issent to treatment location 106. An electronic prescription is sent tothe medication management module 302.

[0041] A computerized physician order entry (CPOE) system can beemployed to carry out some or all of the functions of the prescriptiongeneration module 304. Clinicians 116 can enter data in a variety ofmanners such as, but not limited to, using a tablet wireless computer,medical treatment cart 132, and a workstation.

[0042] Prescription generation can include calculating the dose based onpatient weight and/or height (from the ADT interface 310), the drugamount, diluent volume, concentration, and rate. Prescription generation304 can include confirming operating parameters. The operatingparameters can be based on information from a prescription entry module324. Prescription generation may occur anywhere in the patient caresystem 100 such as, but not limited to, the pharmacy, the treatmentlocation 106, and a nursing center.

[0043] Infusion prescriptions can include prescriptions such as, but notlimited to, single dose infusions, intermittent infusions, continuousinfusions, sequencing, titrating, and alternating types. Infusionprescriptions can also include total parenteral nutritional admixtures(TPN), chemotherapy continuous infusion, piggybacks, large volumeparenterals, and other infusion prescriptions. The patient care system100 is capable of functioning without end dates for orders. The patientcare system 100 can use a continuous schedule generator that looks aheada predefined time period and generates a schedule for admixture fillingfor the time period. The predefined time period can be defined at thepatient care system 100 level or at subsystem levels such as theclinical discipline level and an organizational level. The predefinedtime periods can be adjustable by the clinician 116 entering the order.The schedule can be automatically extendable as long as the order isactive in the patient care system 100.

[0044] The medication management module 302 can interface with more thanone prescription generation module 304. The medication management modulemay receive orders from anywhere within the patient care system 100.

[0045] The pharmacy computer 104 is able to access the electronic copyfrom the medication management module 302. The prescription activationmodule 306 is a computer assisted system for coordinating the fillingand labeling of prescriptions. The filling of the prescription and thecreation or location of medication 124 from stock is handled by theprescription activation module 306.

[0046] While activating the prescription, the prescription activationmodule 306 can calculate the flow rate, if not specified in theprescription, the number of solutions/bags required for a specifiedperiod of time, the time period over which each solution/bag is to beadministered, and the total volume of each solution/bag based on theconcentration of the ingredients in the solution. Flow rates, volume tobe infused, and/or duration may be adjusted in the system 100 whereinthe system will automatically calculate dependent quantities, based oncalculations, if the maximum dosage for the ingredients in theconcentration would be exceeded as identified in the ingredient'smedication file, the patient care system 100 will alert the pharmacistand/or clinician 116 and may ask for a reason code for the adjustment.

[0047] The patient care system 100 may bypass the prescriptionactivation module 306. This may occur if the clinician, such as thepatients' physician, has the authority to immediately activate an order.If the order is immediately activated, the medication management modulemay go directly to prescription labeling module 326.

[0048] In block 326, the patient care system 100 prints the medicationlabel 124. The prescription can be printed remotely and will often beprinted by the pharmacy printer 104 d. After block 326, the patient caresystem goes to block 328. In block 328, the medication label 124 a isattached to the medication 124. The pharmacist generally provides avisual verification 334 that the medication label 124 a matches thefirst hard copy 318 of the prescription. FIG. 3 shows that a visualverification 334 is also associated with prescription authorizationmodule 308. The medication 124 can then be transported from the pharmacyto the treatment location 106. A portable medical treatment cart 132 canbe used for a portion of the route from the pharmacy to the treatmentlocation 106.

[0049] The medication label 124 a can include information for admixing.If not generated within patient care system 100, medication label 124 acan be provided by a bulk medication supplier. If provided by a bulkmedication supplier, the patient care system 100 has the capability ofcoordinating gathering the information from the medication label 124 a.In addition, the patient care system 100 has the ability to addinformation, such as a patient identifier, to medication label 124 a.

[0050] The medication labeling module 328 places the medication label124 on the medication 124. This can be accomplished manually. This canalso be accomplished using an automatic prescription filling andpackaging system (not shown). If an automatic filling and packagingsystem is used, medication labeling module 328 provides data forcoordination of the labeling of the medication 124 to the filling andpackaging system.

[0051] At the treatment location 106, the clinician 116 uses a wirelessdevice 330, such as digital assistant 118 and/or medical treatment cart132, to verify and administer medication 124 to the patient 112.Wireless device 330 communicates with the medication management module302 via a communication path, such as first communication path 126.

[0052] Clinician 116 generally identifies his/herself by scanning herbadge 116 a, identifies the patient 112 by scanning wristband 112 a,identifies the medication 124 by scanning medication label 124 a, andidentifies the medical device 332, such as infusion pump 120, byscanning label 120 d. The clinician 116 may also identify his/herself byproviding a fingerprint and/or password. The medical device 332 may be amedical device capable of two-way communication with the medicationmanagement module 302. Alternatively, the medical device 332 may only becapable of providing information to the medication management module302. Any communication from the medical device 332 will always berecognized as originating from the medical device 332 due to the datastream identification system. The data stream identification systemassists the clinician 116 in administering and verifying the medicaltreatment. In one embodiment, the data stream identification system willgenerally result in the downloading of operating parameters to themedical device 332. The clinician 116 may generally provide a visualverification to confirm the third copy 322 and/or the MAR matches thelabeled medication 124. Scanner 338 may be used to enter machinereadable information from the third copy 322 to the wireless device 330and the medical device 332.

[0053] The patient care system 100 includes the ability to makeadjustments and modifications to infusion orders. Among other modulesthat can include the ability to make infusion adjustments areprescription entry 324, prescription activation 306, prescriptionauthorization 308, and prescription modification module 336. Clinician116 can access prescription modification module 336 in order to makeadjustments to an order. The clinician 116 can access the prescriptionmodification module 336 throughout the patient care system 100. However,one very useful location for the clinician 116 to access theprescription modification module 336 is in the treatment location 106.

[0054] In the prescription authorization module 308, the patient caresystem 100 determines whether the clinician 116 has the authority toindependently modify an infusion order. The clinician 116 can berecognized by the patient care system 100 as having the authority toindependently modify certain portions of the order. If the clinician 116does not have the authority to independently modify the order, apharmacist or physician may be requested to approve the modificationentered by the clinician 116.

[0055]FIG. 4 is a block diagram of a computer 400. Computer 400 may bethe pharmacy computer 104, the central system 108, a CPOE, the digitalassistant 118 of FIG. 1, and/or a computer included in any number ofother subsystems that communicate via the network 102. Computer 400includes an embodiment of the system for uniquely identifying datastreams associated with medical equipment 410. In an embodiment, thesystem for identifying data streams 410 verifies that the rightmedication is provided to the right patient in the right dose at theright time, and via the right route. In another embodiment, the systemfor identifying data streams 410 provides a subset of these desirableverification features. In yet another embodiment, the programming of theinfusion pump 120 can be based on operating parameters received from thepharmacy computer 104, and/or another remote computer. In a furtherembodiment, the programming of the infusion pump 120 can be based onoperating parameters that are confirmed as correct by the pharmacycomputer 104, another remote computer, and/or the clinician 116. Theoperating parameters and/or confirmations can be transported via thecable communication system 110 and the first and second wirelesscommunication paths 126 and 128.

[0056] A critical concern in the art is that the right medication isadministered to the right patient. Therefore, the system for identifyingdata streams 410 includes features to assist in assuring that the rightmedication is administered to the right patient in an efficient manner.The system for identifying data streams 410 of the invention can beimplemented in software, firmware, hardware, or a combination thereof.In one mode, the system for identifying data streams 410 is implementedin software, as an executable program, and is executed by one or morespecial or general purpose digital computer(s), such as a personalcomputer (PC; IBM-compatible, Apple-compatible, or otherwise), personaldigital assistant, workstation, minicomputer, or mainframe computer. Anexample of a general purpose computer that can implement the system foridentifying data streams 410 of the present invention is shown in FIG.4. The system for identifying data streams 410 can reside in, or haveportions residing in, any computer such as, but not limited to, thepharmacy computer 104, the central system 108, and/or the digitalassistant 118. Therefore, computer 400 of FIG. 4 may be representativeof any computer in which the system for identifying data streams 410resides or partially resides.

[0057] Generally, in terms of hardware architecture, as shown in FIG. 4,the computer 400 includes a processor 402, memory 404, and one or moreinput and/or output (I/O) devices 406 (or peripherals) that arecommunicatively coupled via a local interface 408. The local interface408 can be, for example, but not limited to, one or more buses or otherwired or wireless connections, as is known in the art. The localinterface 408 can have additional elements, which are omitted forsimplicity, such as controllers, buffers (caches), drivers, repeaters,and receivers, to enable communications. Further, the local interfacecan include address, control, and/or data connections to enableappropriate communications among the other computer components.

[0058] Processor 402 is a hardware device for executing software,particularly software stored in memory 404. Processor 402 can be anycustom made or commercially available processor, a central processingunit (CPU), an auxiliary processor among several processors associatedwith the computer 400, a semiconductor based microprocessor (in the formof a microchip or chip set), a macroprocessor, or generally any devicefor executing software instructions. Examples of suitable commerciallyavailable microprocessors are as follows: a PA-RISC seriesmicroprocessor from Hewlett-Packard Company, an 80x86 or Pentium seriesmicroprocessor from Intel Corporation, a PowerPC microprocessor fromIBM, a Sparc microprocessor from Sun Microsystems, Inc., or a 68xxxseries microprocessor from Motorola Corporation. Processor 402 can alsorepresent a distributed processing architecture such as, but not limitedto, SQL, Smalltalk, APL, KLisp, Snobol, Developer 400, MUMPS/Magic.

[0059] Memory 404 can include any one or a combination of volatilememory elements (e.g., random access memory (RAM, such as DRAM, SRAM,SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive,tape, CDROM, etc.). Moreover, memory 404 can incorporate electronic,magnetic, optical, and/or other types of storage media. Memory 404 canhave a distributed architecture where various components are situatedremote from one another, but are still accessed by processor 402.

[0060] The software in memory 404 can include one or more separateprograms. The separate programs comprise ordered listings of executableinstructions for implementing logical functions. In the example of FIG.4, the software in memory 404 includes the system for identifying datastreams 410 in accordance with the present invention and a suitableoperating system (O/S) 412. A non-exhaustive list of examples ofsuitable commercially available operating systems 412 is as follows: (a)a Windows operating system available from Microsoft Corporation; (b) aNetware operating system available from Novell, Inc.; (c) a Macintoshoperating system available from Apple Computer, Inc.; (d) a UNIXoperating system, which is available for purchase from many vendors,such as the Hewlett-Packard Company, Sun Microsystems, Inc., and AT&TCorporation; (e) a LINUX operating system, which is freeware that isreadily available on the Internet; (f) a run time Vxworks operatingsystem from WindRiver Systems, Inc.; or (g) an appliance-based operatingsystem, such as that implemented in handheld computers or personaldigital assistants (PDAs) (e.g., PalmOS available from Palm Computing,Inc., and Windows CE available from Microsoft Corporation). Operatingsystem 412 essentially controls the execution of other computerprograms, such as the system for identifying data streams 410, andprovides scheduling, input-output control, file and data management,memory management, and communication control and related services.

[0061] The system for identifying data streams 410 can be a sourceprogram, executable program (object code), script, or any other entitycomprising a set of instructions to be performed. When a source program,the program needs to be translated via a compiler, assembler,interpreter, or the like, which may or may not be included within thememory 404, so as to operate properly in connection with the O/S 412.Furthermore, the system for identifying data streams 410 can be writtenas (a) an object oriented programming language, which has classes ofdata and methods, or (b) a procedural programming language, which hasroutines, subroutines, and/or functions, for example but not limited to,C, C++, Pascal, Basic, Fortran, Cobol, Perl, Java, and Ada. In oneembodiment, the system for identifying data streams 410 is written inC++. In other embodiments, the system for identifying data streams 410is created using Power Builder. The I/O devices 406 may include inputdevices, for example but not limited to, a keyboard, mouse, scanner,microphone, touch screens, interfaces for various medical devices, barcode readers, stylus, laser readers, radio-frequency device readers,etc. Furthermore, the I/O devices 406 may also include output devices,for example but not limited to, a printer, bar code printers, displays,etc. Finally, the I/O devices 406 may further include devices thatcommunicate both inputs and outputs, for instance but not limited to, amodulator/demodulator (modem; for accessing another device, system, ornetwork), a radio frequency (RF) or other transceiver, a telephonicinterface, a bridge, a router, etc.

[0062] If the computer 400 is a PC, workstation, PDA, or the like, thesoftware in the memory 404 may further include a basic input outputsystem (BIOS) (not shown in FIG. 4). The BIOS is a set of essentialsoftware routines that initialize and test hardware at startup, startthe O/S 412, and support the transfer of data among the hardwaredevices. The BIOS is stored in ROM so that the BIOS can be executed whencomputer 400 is activated.

[0063] When computer 400 is in operation, processor 402 is configured toexecute software stored within memory 404, to communicate data to andfrom memory 404, and to generally control operations of computer 400pursuant to the software. The system for identifying data streams 410and the O/S 412, in whole or in part, but typically the latter, are readby processor 402, perhaps buffered within the processor 402, and thenexecuted.

[0064] When the system for identifying data streams 410 is implementedin software, as is shown in FIG. 4, it should be noted that the systemfor identifying data streams 410 can be stored on any computer readablemedium for use by or in connection with any computer related system ormethod. In the context of this document, a computer readable medium isan electronic, magnetic, optical, or other physical device or means thatcan contain or store a computer program for use by or in connection witha computer related system or method. The system for identifying datastreams 410 can be embodied in any computer-readable medium for use byor in connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Inthe context of this document, a “computer-readable medium” can be anymeans that can store, communicate, propagate, or transport the programfor use by or in connection with the instruction execution system,apparatus, or device. The computer readable medium can be for example,but not limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific examples (a non-exhaustive list) of thecomputer-readable medium would include the following: an electricalconnection (electronic) having one or more wires, a portable computerdiskette (magnetic), a random access memory (RAM) (electronic), aread-only memory (ROM) (electronic), an erasable programmable read-onlymemory (EPROM, EEPROM, or Flash memory) (electronic), an optical fiber(optical), and a portable compact disc read-only memory (CDROM)(optical). Note that the computer-readable medium could even be paper oranother suitable medium upon which the program is printed, as theprogram can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted orotherwise processed in a suitable manner if necessary, and then storedin a computer memory.

[0065] In another embodiment, where the system for identifying datastreams 410 is implemented in hardware, the system for identifying datastreams 410 can be implemented with any, or a combination of, thefollowing technologies, which are each well known in the art: a discretelogic circuit(s) having logic gates for implementing logic functionsupon data signals, an application specific integrated circuit (ASIC)having appropriate combinational logic gates, a programmable gatearray(s) (PGA), a field programmable gate array (FPGA), etc.

[0066]FIG. 5 is a flowchart showing an exemplar embodiment 500 of thesystem for identifying data streams 410 of FIG. 4. The system foridentifying data streams 500 is called in block 502. In block 504, thesystem 500 accesses information related to the identity of the clinician116. A first source 506, such as digital assistant 118 may provideinformation related to the identity of the clinician 116. Digitalassistant 118 may acquire the information by reading the clinician'sbadge 116 a with a bar code reader. First source 506 may also be anothercomputer located at the remote location. First source 506 may be othersources of information such as, but not limited to, a bar code, such asa bar code included in clinician's badge 116 a, a tag, laser readabledata, radio-frequency readable data, a keyboard, an iButton reader, afingerprint scanner, and a bar code reader that is not associated withdigital assistant 118. Block 504 may include converting a signalgenerated by first source 506 to a computer readable medium format.Block 504 may also include using the information provided by firstsource 506 to match the information to the identity of the clinician 116through the use of a look-up table stored in memory 404. After block504, the system 500 goes to block 508.

[0067] In block 508, the system 500 identifies the patient 112. Firstsource 506 may provide information related to the identity of thepatient 112. Digital assistant 118 may acquire the information byreading the patient's wristband 112 a with a bar code reader. Block 508may include converting a signal generated by first source 506 to acomputer readable medium format. Block 508 may also include using theinformation provided by first source 506 to match the information to theidentity of the patient 112 through the use of a look-up table stored inmemory 404 or any other matching process. After block 508, the system500 goes to block 510.

[0068] In block 510, the system 500 identifies the treatment. Thetreatment may be the administration of medication 124. First source 506may provide information related to the identity of the treatment. Theidentity of the treatment may include the identification of a medication124. The medication identity may be correlated with a medicationidentifier. The medication identifier may include information such as,but not limited to, a medication identification number, a mixtureidentification number, a patient 112 encounter number, a drug name, adosage, a manufacturer, a batch, an expiration date, and/or a drugprescriber. In block 510, any edubytes, messages, hazard warnings,and/or administrative instructions may be displayed on the digitalassistant 118. Administrative instructions may include specialty set,filter requirements, warnings, and precautions. In block 510, if themedical treatment is a medication, the system 500 may check forexpirations, such as the expiration of an admixture and lot recalls.

[0069] Digital assistant 118 may acquire information by readingmedication label 124 a with a bar code reader. Block 510 may includeconverting a signal generated by first source 506 to a computer readablemedium format. Block 508 may also include using the information providedby first source 506 to match the information to the identity of themedical treatment through the use of a look-up table stored in memory404 or other matching algorithms. After block 510, the system 500 goesto block 512.

[0070] In block 512, the system 500 determines whether the medicaltreatment has been previously associated with patient 112. Thedetermination will often be made by the device that gathers data relatedto the identity of the patient and the medical treatment. For example, aclinician 116 may use the digital assistant 118 as the first source 506to read a bar code from a patient's wristband 112 a. The clinician 116may then use the digital assistant 118 to read medication label 124 a.The digital assistant 118 may then determine whether the patientidentifier from the patient's wristband 112 a is equivalent to thepatient identifier from the medication label 124 a.

[0071] One manner of previously associating the medical treatment withthe patient is to associate the patient and the medical treatment in thecentral system 108 and/or in the pharmacy system 104. A physician maymake the association through a computerized prescription orderingsystem. A pharmacist may make the association by entering a patientidentifier and a medication identifier in the pharmacy system 104 wherethe medication identifier includes the patient identifier. The patientidentifier may be derived from input sources such as, but not limitedto, admission records, orders, an electronic physician order entrysystem, and/or prescriptions.

[0072] If the system 500 determines the medical treatment has not beenpreviously associated with patient 112, the system 500 moves to block516 where an alarm/error status is provided by the system 500. Block 516may include displaying the alarm/error status on the digital assistant118. If the system 500 determines the medical treatment has beenpreviously associated with patient 112, the system 500 moves to block514

[0073] In block 514, the system 500 identifies the medical device. Themedical device is configured to be the type that delivers the medicaltreatment to the patient. For example, the medical device may beinfusion pump 120 if the medical treatment is medication 124. Firstsource 506 may provide information related to the identity of themedical device. Digital assistant 118 may acquire the information byreading label 120 d with a bar code reader. Block 514 may includeconverting a signal generated by first source 506 to a computer readablemedium format. Block 514 may also include using the information providedby first source 506 to match the information to the identity of themedical device through the use of a look-up table stored in memory 404or other matching algorithm. The information related to the identity ofthe medical device may also be stored in the medical device identifier206.

[0074] Block 514 may include identifying sub-systems of the medicaldevice. For example, if the medical device is an infusion pump, theinfusion pump may have multiple channels. The channels may havebarcodes. The channels may be associated with a primary medication and a“piggyback” medication. Block 514 may include identifying thesesub-systems, including piggybacks. After block 514, the system 500 goesto block 518.

[0075] In block 516, the system 500 provides an alarm/error statussignal. The alarm/status signal may be triggered by a variety ofcircumstances such as, but not limited to, the system 500 does notrecognize the patient, the system 500 does not recognize the treatment,the system 500 cannot match the treatment to an order, the system 500cannot identify the medical device 332, the operating parameters are notequivalent, and the treatment parameters are outside the treatmenttolerances. The treatment tolerances may be defined at the patient caresystem 100 level or as a subset of the patient care system 100.

[0076] In block 518, the system for identifying data streams 500determines whether the operating parameters are correct. The operatingparameters are correct if they are consistent with a verified medicaltreatment. The system 500 may include the downloading of operatingparameters to the medical device. The operating parameters may bedownloaded from a variety of sources such as, but not limited to,pharmacy computer 104, medication label 124 a, digital assistant 118,and the clinician 116 may manually enter the operating parameters. Onecheck that may be performed is to confirm the dose is not outside ofpreset tolerances. The operating parameters may be parameters such as,but not limited to, a flow rate per unit of time, a quantity ofmedication, a dosing unit, a dosing duration, a dosing volume, a drugname, a dose unit, and a monitoring limit. The dosing information may beprovided directly or based on patient 112 attributes such as patientweight.

[0077] If the operating parameters are not correct, the system 500 goesto block 516 and returns an error message. If the operating parametersare correct, the system for identifying data streams 500 may display theflow rate and dose information. The display may appear on display 120 c,and/or digital assistant 118.

[0078] In block 520, the system 500 determines whether the treatment iscorrect. The treatment is correct if the treatment is for the patient,the treatment includes the right medication 124, the treatment includesthe correct amount of medication, and the treatment is beingadministered at the right time. The clinician may also be queried toverify the right route by visually inspecting the medical device andrelated equipment. The clinician 116 may change some parameters, such asthe timing of the medical treatment. If changed, a record of the changeis generally kept in the patient care system 100. If the system 500determines the treatment is not correct, the system 500 goes to block516 and provides an error message. If the system 500 determines thetreatment is correct, the system 500 goes to block 522.

[0079] Among the factors that may be considered in determining whetherthe treatment is correct, the system 500 may look to general rules,“look-alike” checks, and “sound-alike” checks. The general rules mayinclude rules, such as but not limited to, a maximum flow rate thatapplies to all medications throughout the treatment facility, a maximumflow rate for the medication, and general rules based on patientcharacteristics, and a combination of these rules.

[0080] In block 522, the system 500 enables the medical device. This mayinclude the clinician 116 providing a start signal to begin theinfusion. In the event the medical device is in delayed start mode,block 520 may include providing a signal that the operating parametershave been downloaded and the medical device should provide the treatmentas soon as the delay period is over. Block 522 may also include queryingthe medical device in order to confirm the correct medical device isbeing used to administer the correct medication to the correct patient.The query may include requesting that the medical device identifier 206provide data to identify the medical device.

[0081] Downloading of operating parameters may include determiningwhether the patient identifier associated with the medical treatmentand/or the patient identifier retrieved from the wristband 112 a, is thesame as the patient identifier associated with the medical treatment atthe central location. The determination will often be made by the firstcomputer, for example, the pharmacy computer 104 a. If the system 500determines the various patient identifiers are not the same the systemmay move to block 516. If the system 500 determines the various patientidentifiers are the same, the system 500 may download the operatingparameters directly to the medical device. The system 500 may send theoperating parameters to a medical device such as infusion pump 120.

[0082] In block 524, the system 500 monitors the administration of themedical treatment. While the system 500 monitors the medical treatmentadministration, any changes to the operating parameters of the pump maybe reflected throughout the patient care system 100 within 10 seconds.The changes may be noted on the digital assistant 118. During theinfusion, the clinician 116 can adjust the infusion parameters. Theadjustment may be to the flow rate of the infusion. Clinician 116generally has the authority to adjust the flow rate within predefinedboundaries. This allows the clinician 116 to “catch-up” if the infusiontubing is blocked or other interruptions occur.

[0083] Block 524 may also include accessing information related to theidentity of a medical device. Accessing information related to theidentity of the medical device may include generating a medical devicetag using the medical device identifier 206. The medical device tagincludes information to uniquely identify the medical device. Block 524may also include accessing information using the data stream identifier204 to generate a unique data tag and attaching the unique data tag todata streams generated by the medical device. The network 102 thenprocesses data streams that include the unique data tag generated by thedata stream identifier 204.

[0084] In block 526, the data stream identification system 500 recordsthe result of the medical treatment administration. The result may bethe successful administration of the medical treatment pursuant to theoperating parameters. However, other results are possible such as, butnot limited to, a patient's refusal to accept the medical treatment, amodification of the medical treatment, and equipment malfunction, and aninterstitial infusion error. In the case of a modification of themedical treatment, a modified order may be generated. The modified ordermay then be linked in the medication management module 302 with theoriginal order.

[0085] Various blocks of the system for identifying data streams 500,such as blocks 518 to 524, may include displaying treatment informationon the digital assistant 118. This may include displaying informationthat mirrors the information on display 120 c of infusion pump 120. Theinformation on display 120 c may be supplemented with information aboutthe patient, the patient location, and the infusion order. Thisinformation may include information regarding multiple channels ofinfusion pump 120. The displayed information may include informationsuch as, but not limited to, personality, prompt line, status line,operating icons and pump head display. Operating icons include fallingdrop, stop sign, flow check piggyback, Guardian, and delay start. Thepump head display includes information such as the drug label and theinfusion rate. Those having ordinary skill in the art are familiar withthe displayed information and operating icons described above.

[0086] In another embodiment, the system for identifying data streams500 may determine there is no information stored in the patient caresystem 100 related to the medical treatment the clinician 116 desires toadminister to the patient 112. If the patient care system 100 recognizesthe clinician 116 as having the authority to initiate the desiredmedical treatment, the system 500 may allow for the administration ofthe medical treatment without going to block 516.

[0087] Throughout this document and the related claims, “centrallocation” and “remote location” are relative terms to each other. A“remote location” is any location where a patient is receiving treatmentthrough a controlled medical device, such as a patient treatmentlocation 106 where patient 112 is receiving treatment through aninfusion pump 120. A “central location” is any location, other than theremote location, where parameters for operating the medical device areaccessible such as, but not limited to, the location of the pharmacycomputer 104 and the central system 108. In a typical arrangement,several remote locations, such as treatment location 106, are incommunication with a central location.

[0088] One benefit of the system for identifying data streams 500 isthat the operating parameters for the medical device do not have to passthrough digital assistant 118, or any other computer in the remotelocation prior to the operating parameters being available to programthe medical device. Bypassing computers at the remote locationeliminates a potential source of errors in administering medication 124to a patient 112. The operating parameters for the medical device may besent “directly” to the medical device assuming the various verificationsare achieved. In this context, “directly” meaning that the operatingparameters may be sent to the medical device without passing through thedigital assistant, or any other computer in the remote location.

[0089] In another embodiment, the system 500 may include an additionalblock (not shown) where the central computer accepts a second medicationidentifier. The second medication identifier may be entered by theclinician 116 at the remote location. The second medication identifiermay be a revised first medication identifier. For example, the secondmedication identifier may be part of the prescription or electronicphysician order entry that is the source for the first patient ID andthe operating parameters. The system 500 may then confirm the first andsecond medication IDs are equivalent prior to sending the operatingparameters to the medical device. The second medication ID may bereplaced by a revised first medication ID between the time theprescription is entered and the time the medication 124 arrives at thetreatment location 106. The system 500 will then sound an alarm ifsecond medication identifier is not equivalent to the first medicationidentifier that was included in the medication label 124 a. In a furtherembodiment, the system 500 may include an additional block (not shown)where the operating parameter is used to program the medical device.

[0090] In one implementation of system 500, an order is entered inpharmacy computer 104. The order includes a first patient identifier andan operating parameter. The pharmacy computer 104 generates a medicationlabel 124 a that is affixed to medication 124. The medication 124 issent to a treatment location 106. At treatment location 106, clinician116 reads the clinician's badge 116 a, patient's wristband 112 a, andmedication label 124 a with a digital assistant 118. The digitalassistant 118 determines whether medication label 124 a and wristband112 a identify the same patient 112. The system 500 then sends themedication identifier to the pharmacy computer 104. The pharmacycomputer 104 confirms the medication label 124 a identifies the samepatient as the order and sends the operating parameter to an infusionpump. The operating parameter may be sent directly to the infusion pump.The operating parameter is then used to program the infusion pump toadminister the medication 124 to the patient 112. The system 500 enablesthe pump and then monitors the treatment. While monitoring thetreatment, the communication from the pump includes accessinginformation related to the identity of the medical device and processingdata streams from the pump that are identified by a unique data tag.Accessing information related to the identity of the medical deviceincludes generating a unique medical device tag. Accessing informationrelated to the identity of the medical device also includes generating aunique data tag using a data stream identifier 204 and attaching theunique data tag to data streams generated by the medical device.

[0091] Any process descriptions or blocks in figures, such as FIG. 3 andFIG. 5, should be understood as representing modules, segments, orportions of code which include one or more executable instructions forimplementing specific logical functions or steps in the process, andalternate implementations are included within the scope of theembodiments of the present invention in which functions may be executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those having ordinary skill in theart.

[0092] It should be emphasized that the above-described embodiments ofthe present invention, particularly, any “preferred” embodiments, aremerely possible examples of implementations, merely setting forth for aclear understanding of the principles of the invention. Many variationsand modifications may be made to the above-described embodiment(s) ofthe invention without substantially departing from the spirit andprinciples of the invention. All such modifications are included withinthe scope of this disclosure and the present invention and protected bythe following claims.

What is claimed is:
 1. A system for identifying data streams,comprising: a medical device generating data streams, the data streamsbeing transmissions of data from the medical device, the data streamsincluding information regarding the operation of the medical device; adata stream identifier generating a unique data tag; a medical deviceidentifier configured to generate a medical device tag upon receipt of arequest from an external computer, the medical device tag includinginformation to uniquely identify the medical device; and, a bridgeconfigured to attach the unique data tag to the data stream, the bridgeconfigured to provide the medical device tag to the external computer,wherein the data stream identifier and the medical device identifier aresecured to the medical device.
 2. The system of claim 1, wherein themedical device is an infusion pump.
 3. The system of claim 1, whereinthe medical device is a ventilator.
 4. The system of claim 1, whereinthe medical device is a monitor of patient status.
 5. The system ofclaim 4, wherein the monitor is an electrocardiogram.
 6. The system ofclaim 4, wherein the monitor is an oxygen monitor.
 7. The system ofclaim 1, wherein the medical device is therapeutic.
 8. The system ofclaim 1, wherein the medical device is diagnostic.
 9. The system ofclaim 1, wherein the medical device is a medical treatment cart.
 10. Thesystem of claim 1, wherein the medical device is a digital assistant.11. The system of claim 1, wherein the data streams include dataregarding the operation of an infusion pump.
 12. The system of claim 1,wherein the data streams include data regarding the status of a patient.13. The system of claim 1, wherein the unique data tag is randomlygenerated after the data stream identifier is secured to the medicaldevice.
 14. The system of claim 1, wherein the medical device tagincludes the medical equipment identifier.
 15. The system of claim 1,wherein the external computer is at a central location.
 16. The systemof claim 1, wherein the external computer is a pharmacy computer. 17.The system of claim 1, wherein the bridge includes a plurality of ports.18. A method for identifying data streams, comprising: providing forgenerating data streams with a medical device, the data streams beingtransmissions of data from the medical device, the data streamsincluding information regarding the operation of the medical device;providing for generating a unique data tag using a data streamidentifier; providing for attaching the unique data tag to the datastreams; and, providing for generating, upon request from an externalcomputer, a medical device tag using a medical device identifier, themedical device tag including information to uniquely identify themedical device, wherein the data stream identifier and the medicaldevice identifier are secured to the medical device.
 19. The method ofclaim 18, wherein the medical device is an infusion pump.
 20. The methodof claim 18, wherein the medical device is a ventilator.
 21. The methodof claim 18, wherein the medical device is a monitor of patient status.22. The method of claim 21, wherein the monitor is an electrocardiogram.23. The method of claim 21, wherein the monitor is an oxygen monitor.24. The method of claim 18, wherein the medical device is therapeutic.25. The method of claim 18, wherein the medical device is diagnostic.26. The method of claim 18, wherein the medical device is a medicaltreatment cart.
 27. The method of claim 18, wherein the medical deviceis a digital assistant.
 28. The method of claim 18, wherein the datastreams include data regarding the operation of an infusion pump. 29.The method of claim 18, wherein the data streams include data regardingthe status of a patient.
 30. The method of claim 18, wherein the uniquedata tag is randomly generated after the data stream identifier issecured to the medical device.
 31. The method of claim 18, wherein themedical device tag includes the medical equipment identifier.
 32. Themethod of claim 18, wherein the external computer is at a centrallocation.
 33. The method of claim 18, wherein the external computer is apharmacy computer.
 34. The method of claim 18, wherein the plurality ofdata streams are transmitted in a network using Bluetooth technology.35. A method for identifying data streams, the method comprising thesteps of: providing for accessing information related to the identity ofa patient; providing for accessing information regarding the identity ofa medical treatment, the medical treatment having a treatment type;providing for determining whether the medical treatment has beenpreviously associated with the patient; providing for providing a firsterror signal if the medical treatment has not been previously identifiedwith the patient; providing for generating a medical device tag toidentify a medical device, the medical device configured to administerthe medical treatment type, the medical device tag including informationto uniquely identify the medical device, the medical device generating aplurality of data streams, the data streams including informationregarding the operation of the medical device; providing for generatinga unique data tag using a data stream identifier; providing forattaching the unique data tag to the data streams generated by themedical device; providing for determining whether a plurality ofoperating parameters for the medical device are consistent with themedical treatment, the operating parameters having been provided from acentral computer, the operating parameters having been provided to themedical device without passing through a remote computer; providing forproviding a second error signal if the operating parameters for themedical device are not consistent with the medical treatment; providingfor enabling the medical device to provide the medical treatment to thepatient; and, providing for verifying that the medical device isproviding the medical treatment to the patient.
 36. The method of claim35, wherein the medical device is an infusion pump.
 37. The method ofclaim 35, wherein the medical device is a ventilator.
 38. The method ofclaim 35, wherein the medical device is a monitor of patient status. 39.The method of claim 38, wherein the monitor is an electrocardiogram. 40.The method of claim 38, wherein the monitor is an oxygen monitor. 41.The method of claim 35, wherein the medical device is therapeutic. 42.The method of claim 35, wherein the medical device is diagnostic. 43.The method of claim 35, wherein the medical device is a medicaltreatment cart.
 44. The method of claim 35, wherein the medical deviceis a digital assistant.
 45. The method of claim 35, wherein the datastreams include data regarding the operation of an infusion pump. 46.The method of claim 35, wherein the data streams include data regardingthe status of a patient.
 47. The method of claim 35, wherein the uniquedata tag is randomly generated after the data stream identifier issecured to the medical device.
 48. The method of claim 35, wherein themedical device tag includes the medical equipment identifier.
 49. Themethod of claim 35, wherein the central computer is at a centrallocation.
 50. The method of claim 35, wherein the central computer is apharmacy computer.
 51. The method of claim 35, wherein the data streamsare transmitted in a network using Bluetooth technology.
 52. The methodof claim 35, wherein the central computer determines whether a pluralityof operating parameters for the medical device are consistent with themedical treatment.
 53. The method of claim 35, wherein accessinginformation related to the identity of a patient includes creating adigital photograph of the patient to compare to a stored digitalphotograph of the patient.
 54. The method of claim 35, wherein themedical treatment includes the use of anesthesiology supplies.
 55. Themethod of claim 35, wherein the medical treatment includes theadministration of a medication and the medication container includes amachine readable label.
 56. The method of claim 35, wherein the centralcomputer determines inventory reorder set points for supplies used forthe medical treatment.
 57. The method of claim 35, wherein the medicaldevice is a medication treatment cart and the central computer providesa signal to access medication.
 58. At least one computer program foridentifying data streams, the at least one computer program includinglogic for: accessing information related to the identity of a patient;accessing information regarding the identity of a medical treatment, themedical treatment having a treatment type; determining whether themedical treatment has been previously associated with the patient;providing a first error signal if the medical treatment has not beenpreviously identified with the patient; generating a medical device tagto identify a medical device, the medical device configured toadminister the medical treatment type, the medical device tag includinginformation to uniquely identify the medical device, the medical devicegenerating a plurality of data streams, the data streams includinginformation regarding the operation of the medical device; generating aunique data tag using a data stream identifier; attaching the uniquedata tag to the data streams generated by the medical device;determining whether a plurality of operating parameters for the medicaldevice are consistent with the medical treatment, the operatingparameters having been provided from a central computer, the operatingparameters having been provided to the medical device without passingthrough a remote computer; providing a second error signal if theoperating parameters for the medical device are not consistent with themedical treatment; enabling the medical device to provide the medicaltreatment to the patient; and verifying that the medical device isproviding the medical treatment to the patient.
 59. The at least onecomputer program of claim 58, wherein the medical device is an infusionpump.
 60. The at least one computer program of claim 58, wherein themedical device is a ventilator.
 61. The at least one computer program ofclaim 58, wherein the medical device is a monitor of patient status. 62.The at least one computer program of claim 61, wherein the monitor is anelectrocardiogram.
 63. The at least one computer program of claim 61,wherein the monitor is an oxygen monitor.
 64. The at least one computerprogram of claim 58, wherein the medical device is therapeutic.
 65. Theat least one computer program of claim 58, wherein the medical device isdiagnostic.
 66. The at least one computer program of claim 58, whereinthe medical device is a medical treatment cart.
 67. The at least onecomputer program of claim 58, wherein the medical device is a digitalassistant.
 68. The at least one computer program of claim 58, whereinthe data streams include data regarding the operation of an infusionpump.
 69. The at least one computer program of claim 58, wherein thedata streams include data regarding the status of a patient.
 70. The atleast one computer program of claim 58, wherein the unique data tag israndomly generated after the data stream identifier is secured to themedical device.
 71. The at least one computer program of claim 58,wherein the medical device tag includes the medical equipmentidentifier.
 72. The at least one computer program of claim 58, whereinthe central computer is at a central location.
 73. The at least onecomputer program of claim 58, wherein the central computer is a pharmacycomputer.
 74. The at least one computer program of claim 58, wherein thedata streams are transmitted in a network using Bluetooth technology.75. The at least one computer program of claim 58, wherein the centralcomputer determines whether a plurality of operating parameters for themedical device are consistent with the medical treatment.
 76. The atleast one computer program of claim 58, wherein accessing informationrelated to the identity of a patient includes creating a digitalphotograph of the patient to compare to a stored digital photograph ofthe patient.
 77. The at least one computer program of claim 58, whereinthe medical treatment includes the use of anesthesiology supplies. 78.The at least one computer program of claim 58, wherein the medicaltreatment includes the administration of a medication and the medicationcontainer includes a machine readable label.
 79. The at least onecomputer program of claim 58, wherein the central computer determinesinventory reorder set points for supplies used for the medicaltreatment.
 80. The at least one computer program of claim 58, whereinthe medical device is a medication treatment cart and the centralcomputer provides a signal to access medication.
 81. An apparatuscomprising: a medical device having a data output comprising medicaltreatment information; a wireless device coupled to the data output andhaving a radio frequency (RF) output; a medical device tag associatedwith the medical device and comprising information to uniquely identifythe medical device, the information provided upon request by anelectronic device; a data stream identifier having an identifier outputattached to the medical treatment information.
 82. The apparatus ofclaim 81, wherein the medical device is an infusion pump.
 83. Theapparatus of claim 82, the medical treatment information comprising afluid flow rate.
 84. The apparatus of claim 83, wherein the medicaldevice was originally manufactured without a wireless device.